fix: handle case where constraint.relations=None#33
Merged
jsstevenson merged 4 commits intomainfrom Feb 12, 2026
Merged
Conversation
korikuzma
reviewed
Feb 12, 2026
Collaborator
korikuzma
left a comment
korikuzma
left a comment
There was a problem hiding this comment.
Looks good, can you add or update a test for this?
Contributor
Author
|
...huh |
korikuzma
approved these changes
Feb 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If the constraint's
relationsproperty is set toNone(which is legal), line 183 raises aNoneTypeError, which is not properly handled byvalidate_constraints. This small fix makes errors a bit more interpretable in those cases.priority:low